System and method for candidate domain name generation

ABSTRACT

A system and method for the generation of candidate domain names are presented. The method includes receiving, by at least one server communicatively coupled to a network, a request to access or purchase access to a software application, the request being received from a user. Keywords associated with at least one of the user, a website of the user, and a business of the user are generated and a candidate domain name relevant to the keywords is generated. A user interface is displayed including the candidate domain name. The user interface enables the user to register the candidate domain name.

FIELD OF THE INVENTION

The present invention relates generally to the generation of candidatedomain names and, more particularly, to systems and methods forproviding users one or more candidate domain names based on informationaccumulated while a user processes a transaction.

BACKGROUND OF THE INVENTION

A network is a collection of links and nodes (e.g., multiple computersand/or other devices connected together) arranged so that informationmay be passed from one part of the network to another over multiplelinks and through various nodes. Examples of networks include theInternet, the public switched telephone network, the global Telexnetwork, computer networks (e.g., an intranet, an extranet, a local-areanetwork, or a wide-area network), wired networks, and wireless networks.

The Internet is a worldwide network of computers and computer networksarranged to allow the easy and robust exchange of information betweencomputer users. Hundreds of millions of people around the world haveaccess to computers connected to the Internet via Internet ServiceProviders (ISPs). Content providers place multimedia information (e.g.,text, graphics, audio, video, animation, and other forms of data) atspecific locations on the Internet referred to as web pages. Websitescomprise a collection of connected, or otherwise related, web pages. Thecombination of all the websites and their corresponding web pages on theInternet is generally known as the World Wide Web (WWW) or simply theWeb.

For Internet users and businesses alike, the Internet continues to beincreasingly valuable. More people use the Web for everyday tasks, fromsocial networking, shopping, banking, and paying bills to consumingmedia and entertainment. E-commerce is growing, with businessesdelivering more services and content across the Internet, communicatingand collaborating online, and inventing new ways to connect with eachother.

Prevalent on the Web are multimedia websites, some of which may offerand sell goods and services to individuals and organizations. Websitesmay consist of a single webpage, but typically consist of multipleinterconnected and related web pages. Websites, unless extremely largeand complex or exposed to unusual traffic demands, typically reside on asingle server and are prepared and maintained by a single individual orentity. Menus and links may be used to move between different web pageswithin the website or to move to a different website as is known in theart. The interconnectivity of web pages enabled by the Internet can makeit difficult for Internet users to tell where one website ends andanother begins.

Websites may be created using HyperText Markup Language (HTML) togenerate a standard set of tags that define how the web pages for thewebsite are to be displayed. Users of the Internet may access contentproviders' websites using software known as an Internet browser, such asMICROSOFT INTERNET EXPLORER or MOZILLA FIREFOX. After the browser haslocated the desired webpage, the browser requests and receivesinformation from the webpage, typically in the form of an HTML document,and then displays the webpage content for the user. The user then mayview other web pages at the same website or move to an entirelydifferent website using the browser.

Some Internet users, typically those that are larger and moresophisticated, may provide their own hardware, software, and connectionsto the Internet. But many Internet users either do not have theresources available or do not want to create and maintain theinfrastructure necessary to host their own websites. To assist suchindividuals (or entities), hosting companies exist that offer websitehosting services. These hosting service providers typically provide thehardware, software, and electronic communication means necessary toconnect multiple websites to the Internet. A single hosting serviceprovider may literally host thousands of websites on one or more hostingservers.

Browsers are able to locate specific websites because each website,resource, and computer on the Internet has a unique Internet Protocol(IP) address. Presently, there are two standards for IP addresses. Theolder IP address standard, often called IP Version 4 (IPv4), is a 32-bitbinary number, which is typically shown in dotted decimal notation,where four 8-bit bytes are separated by a dot from each other (e.g.,64.202.167.32). The notation is used to improve human readability. Thenewer IP address standard, often called IP Version 6 (IPv6) or NextGeneration Internet Protocol (IPng), is a 128-bit binary number. Thestandard human readable notation for IPv6 addresses presents the addressas eight 16-bit hexadecimal words, each separated by a colon (e.g.,2EDC:BA98:0332:0000:CF8A:000C:2154:7313).

IP addresses, however, even in human readable notation, are difficultfor people to remember and use. A Uniform Resource Locator (URL) is mucheasier to remember and may be used to point to any computer, directory,or file on the Internet. A browser is able to access a website on theInternet through the use of a URL. The URL may include a HypertextTransfer Protocol (HTTP) request combined with the website's Internetaddress, also known as the website's domain name. An example of a URLwith a HTTP request and domain name is: http://www.companyname.com. Inthis example, the “http” identifies the URL as a HTTP request and the“companyname.com” is the domain name.

Domain names are easier to remember and use than their corresponding IPaddresses. The Internet Corporation for Assigned Names and Numbers(ICANN) approves some Generic Top-Level Domains (gTLD) and delegates theresponsibility to a particular organization (a “registry”) formaintaining an authoritative source for the registered domain nameswithin a TLD and their corresponding IP addresses. For certain TLDs(e.g., .biz, info, .name, and .org) the registry is also theauthoritative source for contact information related to the domain nameand is referred to as a “thick” registry. For other TLDs (e.g., .com and.net) only the domain name, registrar identification, and name serverinformation is stored within the registry, and a registrar is theauthoritative source for the contact information related to the domainname. Such registries are referred to as “thin” registries. Most gTLDsare organized through a central domain name Shared Registration System(SRS) based on their TLD.

The process for registering a domain name with .com, .net, .org, andsome other TLDs allows an Internet user to use an ICANN-accreditedregistrar to register their domain name. For example, if an Internetuser, John Doe, wishes to register the domain name “mycompany.com,” JohnDoe may initially determine whether the desired domain name is availableby contacting a domain name registrar. The Internet user may make thiscontact using the registrar's webpage and typing the desired domain nameinto a field on the registrar's webpage created for this purpose. Uponreceiving the request from the Internet user, the registrar mayascertain whether “mycompany.com” has already been registered bychecking the SRS database associated with the TLD of the domain name.The results of the search then may be displayed on the webpage tothereby notify the Internet user of the availability of the domain name.If the domain name is available, the Internet user may proceed with theregistration process. If the domain name is not available forregistration, the Internet user may keep selecting alternative domainnames until an available domain name is found.

For many users that wish to have an Internet presence, the selection ofa particular domain name may be secondary consideration. Some users, forexample, may desire to construct a website and may even have a vagueunderstanding of the concept of a domain name, but may not understandthat a domain name must be registered before the website can be hostedthere. Other users may have already registered a domain name, but maynot understand that a domain name must, in many cases, be selected inorder optimize the search engine performance of the domain name andassociated website. For example, a customer may wish to purchaseadvertising services for a website at a particular domain name, but maynot understand that the domain name is a poor match for the desiredadvertising. In such a case, the user may observe better performance forthe advertising if the user were to register a new, better suited,domain name and host the website on that domain name.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a possible embodiment of a system for generating acandidate domain name.

FIG. 2 is a flowchart illustrating a method for generating candidatedomain names based on data received during purchase or use of a softwareapplication or service.

FIG. 3 is a flowchart illustrating a method for generating candidatedomain names based on data related to a website builder application.

FIG. 4 is a flowchart illustrating a method for generating candidatedomain names based on data received from a user and a third party datasource.

FIG. 5 is a flowchart illustrating a method for generating candidatedomain names based on data relating to advertising services.

FIG. 6 illustrates a possible embodiment of a system for generating thecandidate domain name.

FIG. 7 illustrates a possible embodiment of a server included in thesystem of FIG. 6.

FIG. 8A is a screenshot showing an example user interface by which therequester can build a website using a website builder application.

FIG. 8B is a screenshot showing an example form the requester cancomplete to provide input data while using a website builderapplication.

FIG. 8C is a screenshot showing an example checkout page user interfaceincluding a candidate domain name.

FIG. 8D is a screenshot showing a website builder user interfaceincluding a candidate domain name.

FIG. 9A is a screenshot showing an example user interface by which therequester can link a user account to a third party data source.

FIG. 9B is a screenshot showing an example confirmation page by whichthe requester can confirm linkage of their user account to the thirdparty data source.

FIG. 10 is a screenshot showing an example website information page bywhich the requester can complete a website information form to provideinput data while using an advertising software application provided bythe registrar.

FIG. 11 is a screenshot showing an example user interface providing adashboard of an advertising campaign and including a candidate domainname.

DETAILED DESCRIPTION

The present invention relates generally to the generation of candidatedomain names and, more particularly, to systems and methods forproviding users one or more candidate domain names based on informationaccumulated while a user processes a transaction.

In one implementation, the present disclosure provides a methodincluding receiving, by at least one server communicatively coupled to anetwork, a request to access or purchase access to a softwareapplication. The request is received from a user. The method includesidentifying, by the at least one server, keywords associated with atleast one of the user, a website of the user, and a business of the userand generating, by the at least one server, a candidate domain namerelevant to the keywords. The method includes displaying, by the atleast one server, a user interface including the candidate domain name,the user interface enabling the user to register the candidate domainname.

In another implementation the present disclosure provides a methodincluding receiving, by at least one server communicatively coupled to anetwork, data relating to interactions of a user with a website, andgenerating keywords associated with at least one of the user, a websiteof the user, and a business of the user based on the interactions of theuser. The method includes generating, by the at least one server, acandidate domain name relevant to the keywords, and returning, by the atleast one server, the candidate domain name.

In another implementation, the present disclosure provides a systemincluding at least one server computer in communication with a network.The at least one server computer includes a processor configured toreceive a request to access or purchase access to a softwareapplication. The request is received from a user. The processor isconfigured to generate keywords associated with at least one of theuser, a website of the user, and a business of the user, generate acandidate domain name relevant to the keywords, and display a userinterface including the candidate domain name, the user interfaceenabling the user to register the candidate domain name.

A user operating hosted software applications (e.g., website builders,email, website hosting, storage, auctions, advertising, etc.) orbrowsing for and purchasing the same often provides a large amount ofinformation, either personal or business related, to the host of thoseapplications, such as a registrar. Many users, however, may notunderstand or want to take the steps necessary to search for andregister a domain name while utilizing the client software applicationsor browsing for and purchasing the same. Therefore, the present systemcan monitor the user's activities and provide the user with a listing ofrelevant candidate domain names, as an automated process, based on theinformation provided by the user during interaction with the clientsoftware applications. If the user, upon reviewing one or more of theprovided candidate domain names, wishes to register one of the candidatedomain names, the user can select the desired domain name and undertakea registration procedure.

FIG. 1 is a system 100 for generating one or more candidate domain namesfor a user 102 accessing a website 106. The website 106 may, forexample, include a website or web service hosted by a registrar or otherentity. The website 106 may provide one or more software applications108 (e.g., website builders, email, website hosting, storage, auctions,advertising, etc.) for purchase or with which the user 102 can interact.As the user 102 interacts with the plurality of client softwareapplications 108, the user 102 provides input data (e.g., personalinformation or business information) that can be stored in a customerdatabase 130 hosted on a server 110 hosting website 106. The server 110hosting the website 106 can process the input data provided by the user102 and analyze that input data to generate candidate domain names forpurchase using a checkout feature 112. The website 106 can then providethose relevant candidate domain names to the user 102, for example,while the user 102 is purchasing or otherwise operating one of theplurality of client software applications 108 or is otherwiseinteracting with one or more software applications 108 hosted by server110. Optionally, the server 110 may gather and process additional dataand information about the user 102 from third party data sources 104(e.g., FACEBOOK, LINKEDIN, YELP, TWITTER, State Bar, etc.) based on theinput data provided by the user 102 in order to provide a more relevantcandidate domain name to the user or the user's business.

In general, the present system allows for the monitoring of the actionsof a user while that user interacts with a website. The interactions mayinvolve the user shopping for (e.g., searching for informationdescribing) and purchasing goods or services or utilizing one or morehosted software application provided by the website. As the userinteracts with the website, the user is providing information to thewebsite, either explicitly or implicitly. For example, the user mayexplicitly provide information during a user account creation process orproduct research and product purchase and checkout process. Similarly,the user may input information into one or more software application,such as a website builder or advertising service. Alternatively, theuser may implicitly provide information, such as the user's location,products that were searched for and reviewed by the user, but notpurchased, and the like. As described below, this information can becollected and analyzed to generate a set of candidate domain names thatmay be displayed to the user for purchase, where the candidate domainnames are relevant to the user, or, for example, the user's business.

FIG. 2 is a flowchart illustrating a method by which candidate domainnames can be generated for the user 102 based on data received from theuser 102 during an acquisition of a software application or service. Themethod may be useful, for example, to assist users that are shopping forand purchasing Internet services that typically require the user to alsohave a domain name to select and register an appropriate domain name. Auser, for example, may be shopping for hosting services, but not realizethat the hosted content would typically be accessed through a domainname. In that case, the method illustrated in FIG. 2 may be utilized toprovide the user with a listing of candidate domain names of which theymay wish to purchase one in combination with their hosting services. Inother cases, users may be browsing available services and not evenrealize that they would like to register a domain name. In that case,while the user browses the available services, they can also be providedwith a listing of domain names that are relevant to them for selectionand registration.

The user 102 begins by accessing the website 106. The user 102 may beany Internet user, for example, who may wish to establish an onlinepresence and may subsequently access the website 106, such asGODADDY.COM's website, to purchase one or more online services. In step200, the user 102 is authenticated as either an existing user or a newuser. If the user 102 is an existing user, the website 106 provides theuser 102 with product and service options for purchase at step 206 oncethe user 102 has logged in with their credentials (i.e., username andpassword). If the user 102 is a new user, a new user account may begenerated at step 202. Once the user account is generated, the website106 provides the user 102 with a listing of the plurality of clientsoftware applications or services 208 for purchase at step 206. In otherimplementations, the process may be reversed with the user firstbrowsing available product and service options and, after selecting oneor more for purchase, authenticating to the website 106 or creating anew user account. The plurality of client software applications andservices 208, as a non-limiting example, may include a website builder,website hosting services, search engine visibility (i.e., advertising)services, online storage and/or email applications.

At step 210, once the user has selected one of the software applicationsor services 208 for purchase, one or more order forms, as will bediscussed in further detail below, is displayed to the user 102 on auser interface. The form may vary depending on which of the plurality ofclient software applications 208 the user 102 has requested. Generally,the form prompts the user 102 to provide any additional information, ifnecessary, for the requested services to be provided to the user 102.For example, the form may be a user information form, a businessinformation form, a user contact information form, a website informationform or order form requesting specific user 102 information andproviding blanks for the user 102 to enter personal and/or businessrelated data through the user interface. As the user 102 completes theform, the information provided by the user 102 is captured. For example,the form may request that the user 102 provide input data 214 thatincludes, but is not limited to, a title (e.g., a business name), alocation (e.g., home and/or business address, city, state, zip code,etc.), a phone number, features relevant to the user's 102 products andservices that may be offered by the user's business, email address,text, and metadata such as images provided by the user 102 to thewebsite 106 at step 212. In some implementations, some or all of thedata requested by the order form may be populated with informationretrieved from the user's account information. In that case, a fellableorder form may not be displayed for the user. Instead, the form may beautomatically created and the user may simply be provided with a userinterface allowing the user to confirm that they wish to purchase theselected software application.

As the user 102 is providing the input data 214, the system 100 may beconfigured to acquire additional data about the user 102 from thirdparty data sources 204 at step 216. For example, if the user 102provides their first and last name on the form (or that information canbe retrieved from the user's account), the system 100 may run a searchon the third party data sources 204 using the user's 102 first and lastname to gather additional information about the user 102. The thirdparty data sources 204 may include, but are not limited to, LINKEDIN,FACEBOOK, YELP, TWITTER, and a State Bar directory.

As a non-limiting example, the system 100 may run a search onFacebook.com using the first and last name provided by the user 102. Thesystem 100 may gather information from Facebook.com, such as where theuser 102 is from (i.e., city and state), where they are employed, whatcollege they attended, etc.

In step 218, the system 100 combines the data collected about the userin steps 212 and 216 into a collection of keywords, referred to hereinas a keyword collection. These keywords (in combination with any otherdata collected about the user 102) will be used to generate one or morecandidate domain names for the user 102, as will be discussed in furtherdetail below. In some implementations, additional sources of informationmay be used to collect information about the user 102 that may beutilized to make candidate domain name recommendations. Exampleadditional sources include those that include the product search historyof the user, the user's purchase history, a listing of other products orservices that have already been purchased by the user, the user'scustomer information, and the like.

After the collection of keywords has been generated, the system 100 canuse that collection of keywords to generate one or more candidate domainnames for the user 102 that the user 102 may wish to purchase. In somecases, this will involve analyzing, in addition to the collection ofkeywords, websites of third parties that are relevant to the user or theuser's business. In that case, the content of those third party websitescan be analyzed to potentially generate additional keywords from whichthe candidate domain names can be generated or to determine the qualityof one or more of the candidate domain names. In some implementations,the system 100 will also determine whether the generated candidatedomain names are actually available to be registered. If, for example, aparticular candidate domain name has already been registered, thatcandidate domain name will not be displayed to the user for purchase.

For example, if the user 102 provided input data 214 at step 212 thatincluded words such as “menu” or “food”, the system 100 may includethese words in the keyword collection at step 218. The words “menu” and“food” from the keyword collection can then be compared to other relatedwebsites, such as other restaurant websites, in order to generate one ormore candidate domain names relevant to the user's 102 input data 214 atstep 222. The candidate domain names provided at step 222 are,therefore, domain names that are relevant to the user 102 and areprovided to the user 102 who may not have otherwise been searching for adomain name. Alternatively, if the user 102 was searching for a domainname on the domain name registration website 106, the system 100 mayprovide the user 102 a link (not shown) to buy more or similar domainnames based on the input data 214 and additional data acquired from thethird party data sources 204.

In some implementations, the system 100 checks to see if the useralready has a registered domain name. If so, the identification of suchother domain names can be used to prevent the system 100 from suggestingcandidate domain names that are too similar to domain names alreadyregistered by the user 102.

In one embodiment of the present invention, the system 100 may beconfigured to only provide the candidate domain name or alternativedomain name at step 222 if a minimum data requirement is met. Forexample, a new user may utilize one of the client software applications208 provided by the website 106 and only provide input data 214 thatincludes their name and email address, for example, at step 212. Theminimum data requirement provided by the system 100 may require aminimum of three pieces of information relevant to the user 102. As anon-limiting example, the minimum data requirements may be a name, emailaddress and a location provided by the user 102, either implicitly orexplicitly, in order for the system 100 to suggest the candidate oralternate domain name at step 222. Therefore, if the user 102 onlyprovides two pieces of information at step 212, the system may notgenerate a candidate or alternate domain name at step 222. This minimumdata requirement provided by the system 100 may ensure that thecandidate and alternate domain names generated at step 222 are in factrelevant to the user 102 based on the keyword collection generated atstep 218. Alternatively, a relevance score may be internally generatedby the system 100 for the candidate or alternate domain name at step 222based on the keyword collection currently available. If the relevancescore is greater than a predefined threshold, for example, the candidateor alternate domain name would be displayed to the user 102.

Once a candidate domain name or an alternate domain name is generatedbased on the keyword collection at step 222, the system 100 may providethe user 102 an option to add the domain name to their shopping cart atstep 224 for purchase. Step 224 may occur, for example, as the user isgoing through a checkout process 112 for purchase of the client softwareapplication 208. At step 226, the user 102 may checkout and purchase theclient software application 208 and, optionally, the domain namegenerated at step 222.

To illustrate, FIG. 8C is a screenshot showing an example checkout pageuser interface including a candidate domain name. As shown in FIG. 8C,candidate domain name 834 may be displayed to the user 102 on thewebsite 106. For example, the candidate domain name 834 may be‘mikesrestaurant.com’ based on the keywords generated at step 218 of themethod of FIG. 2. The candidate domain name 834 may be displayed whilethe user 102 is going through a checkout process 112 for a websitebuilder application 808, for example. Alternatively, the candidatedomain name 834 may be displayed while the user 102 is going through acheckout process 112 for an alternative product or service, such asthose provided at step 206 of FIG. 2. The user 102 may choose to add thecandidate domain name 834 to their shopping cart by selecting an ‘Add’button 836. The user 102 may select a ‘checkout’ button 838 to completetheir purchase of the website builder application 808 and, optionally,the domain name 834 generated at step 222.

Turning now to FIG. 3, a flowchart illustrating a method by whichcandidate domain names can be generated for the user 102 based on datareceived by the user 102 while utilizing a software application orservice, such as a website builder 808, shown in FIG. 8A, is shown.Although the present flowchart and method is described in terms of auser utilizing a specific type of software application (i.e., a websitebuilder), the methods illustrated in FIG. 3 and described herein may beutilized in conjunction with a user utilizing any software applicationthat involves the user supplying information, either explicitly orimplicitly, to a software application. For example, the method may beutilized to provide a user with a listing of candidate domain names forpurchase while the user is interacting with email software, web hostingmanagement software, accounting software, and the like.

Similarly to the flowchart illustrated in FIG. 2, the user 102 begins byaccessing the website 106. In step 300, the user 102 is authenticated aseither an existing user or a new user. If the user 102 is an existinguser, the website 106 provides the user 102 access to the websitebuilder application 808 at step 306 once the user 102 has logged in withtheir credentials (i.e., username and password). If the user 102 is anew user, a new user account may be generated at step 302. Once the useraccount is generated, the website 106 provides the user 102 the websitebuilder application 808 at step 306.

As a new user, the website builder application 808 will provide the user102 a plurality of website templates (not shown) to begin building theirwebsite. The website templates are pre-designed and may be related tocategories such as business and services, music, entertainment, onlineshop, restaurant and hospitality, photography, design, retail andfashion, personal, etc. Once a template is selected, the user 102 canbegin building a website using the website builder application 808. Assuch, the user 102 is provided with a user interface 810, such as thatshown in FIG. 8A. Within the interface, menu options 812 may be providedon the user interface 810 to assist the user 102 in building theirwebsite. Beginning with a home page, as shown in FIG. 8A, the user 102may add a content block 814 to the website, for example, that gives abrief description of the website being built. The user 102 simply dragsa content block icon 816 to the desired location on the user interface810 and the user 102 can type directly into the content block 814.

Additionally, the user 102 may add an image 818 (e.g., a company logo)to the home page of the website by simply dragging the image icon 820 tothe desired location on the user interface 810. The image 818 may beprovided by the user 102 or may be a stock image provided by the websitebuilder application 808. Similarly, the user has the option to add imagegalleries or video, for example, to their website by simply dragging animage gallery icon 822 or a video icon 824 to the desired location onthe user interface 810. The user 102 further has the option to addadditional pages to their website by selecting the pages 826 menuoption. Other pages 826, may include, but are not limited to, a sitegallery page, an about us page, a contact information page, an onlinestore page, a site map, a forum page, etc. The user 102 also has theoption to provide a link to their social web pages (e.g., LINKEDIN,TWITTER, FACEBOOK, etc.) by selecting a social menu option 828, as willbe discussed in further detail below.

Returning to the flowchart illustrated in FIG. 3, the user 102 maynavigate, edit, and update their website using the website builderapplication 808 as described above and provided at step 306. At step310, while the user 102 edits their website using the website builderapplication 808, various forms, such as user information forms, businessinformation forms, user contact forms, website information forms, etc.,may be provided to the user 102 for the user 102 to complete. Forexample, when the user 102 adds a content block 814 to the website, addsimages 818, image galleries, videos or updates a contact informationpage 830, as shown in FIG. 8B, each action may involve the usercompleting forms other otherwise providing information to the websitebuilder application 808. The forms may vary depending on which menuoption 814 the user 102 is utilizing. In some cases, the forms includeexplicit user input devices (e.g., textboxes, check boxes, radiobuttons, and the like) into which the user provides input.Alternatively, the forms may be incorporated into other user interfacesallowing the user to added content to or revise content within theuser's website. For example, the interface through which the user addsimages to their website is considered a form, as is the mechanism bywhich the user adds video. Regardless of the menu options 812 beingused, the server 110 shown in FIG. 1 acquires data from the user 102 asthe user manipulates their website using the website builder application808.

For example, the user 102 may fill out a user contact information form832 while creating or editing the contact information page 830 of theirwebsite, as shown in FIG. 8B. The user contact information form 832 mayenable the user 102 to provide input data 314 such as a first name, lastname, address, city, state, zip code, phone number, etc. Returning toFIG. 2, after capturing the input data 314, the system 100 may beconfigured to acquire additional data about the user 102 or the user'sbusiness from third party data sources 304 at step 316. For example, ifthe user 102 provides their first and last name on the user contactinformation form 832, the system 100 may run a search on the third partydata sources 304 using the user's 102 first and last name to gatheradditional information about the user 102. The third party data sources304 may include, but are not limited to, LINKEDIN, FACEBOOK, YELP,TWITTER and a State Bar directory. As a non-limiting example, the system100 may run a search on Facebook.com using the first and last nameprovided by the user 102. The system 100 may gather information fromFacebook.com, such as where the user 102 is from (i.e., city and state),where they are employed, what college they attended, etc.

The system 100 provides an integration module (not shown) to generate akeyword collection at step 318 by running a content analysis (e.g.,crawl) on the website being built by the user 102 that identifieskeywords throughout the pages of the website. The keyword collection maycontain, for example, keywords related to the user 102 acquired at steps312 and 316, keywords selected from title text on the user's website,and information collected from third party sources about the user or theuser's business. A cache storage database 319 may be provided by thesystem 100 to store the input data 314 provided by the user 102 at step312 and to store data related to the user 102 acquired from the thirdparty data sources 304 at step 316. The keywords generated at step 318will be used to generate a candidate domain name for the user 102, aswill be discussed in further detail below.

After the collection of keywords has been generated, the system 100 canuse that collection of keywords to generate one or more candidate domainnames for the user 102 that the user 102 may wish to purchase. In somecases, this will involve analyzing, in addition to the collection ofkeywords, websites of third parties that are relevant to the user or theuser's business. In that case, the content of those third partywebsite's can be analyzed to potentially generate additional keywordsfrom which the candidate domain names can be generated.

In some implementations, the system 100 checks to see if the useralready has a registered domain name. If so, the identification of theseother domain names can be used to prevent the system 100 from suggestingcandidate domain names that are too close to domain names alreadyregistered by the user 102.

Once a candidate domain name or an alternate domain name is generatedbased on the keyword collection at step 322, the system 100 may providethe user 102 an option to add the domain name to their shopping cart atstep 324 for purchase as part of the website builder interface. Forexample, FIG. 8D shows a web site builder user interface 808 (e.g., theuser interface of FIG. 8A), modified to incorporate or display candidatedomain name 834 that may be offered for purchase by the user. Candidatedomain name 834 may be displayed on each user interface screen presentedby the web site builder interface until, for example, candidate domainname 834 is either dismissed by the user, or the user decides topurchase or register the candidate domain name. Candidate domain name834 may only be displayed in the user interface once sufficient keywordshave been collected to generate a candidate domain name with sufficientconfidence. With reference to FIG. 8D, the user can choose to add thecandidate domain name 834 to their shopping cart by selecting an ‘Add’button 836. The user will then be given an opportunity to purchase orregister the domain name.

Returning to FIG. 3, at step 325, the user 102 may choose to add thecandidate domain name 834 to their shopping cart by selecting an ‘Add’button 836. At step 326, the user 102 may select a ‘checkout’ button 838to complete their purchase of the website builder application 808 and,optionally, the domain name 834 generated at step 322.

As indicated by step 325, if the user 102 does not elect to purchase oneof the candidate domain names, the method repeats and the system 100continues providing the website builder application to the user andmonitoring the user's actions. As such, additional revisions or changesto the user's website can be captured, in which case a new listing ofcandidate domain names may be generated and displayed for purchase bythe user 102. Accordingly, if the user 102 does not elect to purchaseone of the candidate domain names, the system 100 returns to step 306 toagain provide the website builder application to the user and monitorwhether the user 102 is updating or adding data 314 to their website.During this process, the system 100 provides the cache storage 319 inorder to store the recently updated and added data 314, as well as thedata acquired from third party data sources 304. In this sense, thesystem 100 may access the cache storage 319 to quickly generate eitherthe candidate or alternate domain name at step 322 and provide the user102 the option to add the domain name to their shopping cart at step324.

In various implementations, the method illustrated in FIG. 3 may becontinually executed as the user interacts with and utilizes the websitebuilder application (or other software application). As such, thelisting of candidate domain names can be continually updated as the userinteracts with the software, providing new information and/or revisingexisting information. As such, while the user utilizes the softwareapplication, the listing of candidate domain names will continuously berefreshed and will always represent a list of potential domain namesthat are closely relevant to the content being supplied by the user intothe software application.

Turning now to FIG. 4, a flowchart illustrating a method by whichcandidate domain names can be generated for the user 102 based on dataacquired from third party data sources 404 is shown. The user 102 inthis case may be an existing user and may begin by accessing the website106. In step 400, the user 102 is authenticated as an existing user.Once authenticated, the user may begin using one or more softwareapplications made available by the website 106 or may access the user'saccount information. While interacting with the website 106, the user102 determines that he or she wishes to link their account to anexternal third party account. Accordingly, while interacting with thewebsite 106 the user 102 may activate a user interface enabling the userto begin the process of linking their account with a third partyaccount. The process of linking the user's 102 account with a thirdparty account may be accomplished at a user account level.

At step 409, the system 100 prompts the user 102 to link their existinguser account to a third party account 404. As a non-limiting example,the third party account 404 may include the user's 102 LINKEDIN,FACEBOOK, YELP, State Bar or TWITTER account. At step 410, a userinformation form 932, as shown in FIG. 9A, is provided to the user 102.The user information form 932 may include, for example, a login window940 that enables the user 102 to log into their third party account 404and grant the system 100 permission to access the third party account404. In order to link the third party account 404 (e.g., a socialnetwork account), the system 100 may use standard connection protocolsprovided by the third party data sources such as, FACEBOOK connect,FACEBOOK pages or LINKEDIN Company page. Alternatively, the system 100may request that the user 102 provide their public URL to third partydata sources (e.g., TWITTER handle, YELP URL). Once linked, averification screen 942, as shown in FIG. 9B, may appear on the websiteof the user's 102 third party data source confirming that their useraccount is now linked and has access to the information provided by thethird party data source. The system 100 may then acquire data about theuser 102 from the newly linked third party data sources 404 at step 416.For example, the system 100 may run a search on the third party datasources 404 using the user's 102 first and last name to gatheradditional information about the user 102. The third party data sources404 may include, but are not limited to, LINKEDIN, FACEBOOK, YELP,TWITTER and a State Bar directory. The system 100 may gather informationfrom Facebook.com, for example, such as where the user 102 is from(i.e., city and state), where they are employed, what college theyattended, etc.

The system 100 provides an integration module (not shown) to generate akeyword collection at step 418. The keyword collection may contain, forexample, keywords related to the user 102 acquired at step 416. Thesekeywords will be used to generate a candidate domain name for the user102, as will be discussed in further detail below.

After the collection of keywords has been generated, the system 100 canuse that collection of keywords to generate one or more candidate domainnames for the user 102 that the user 102 may wish to purchase. In somecases, this will involve analyzing, in addition to the collection ofkeywords, websites of third parties that are relevant to the user or theuser's business. In that case, the content of those third partywebsite's can be analyzed to potentially generate additional keywordsfrom which the candidate domain names can be generated.

In some implementations, the system 100 checks to see if the useralready has a registered domain name. If so, the identification of theseother domain names can be used to prevent the system 100 from suggestingcandidate domain names that are too close to domain names alreadyregistered by the user 102.

Once a candidate domain name or an alternate domain name is generatedbased on the keyword collection at step 422, the system 100 may providethe user 102 an option to add the domain name to their shopping cart atstep 424 for purchase. Step 424 may occur, for example, as the user isgoing through a checkout process 112 for a client software application408 or is otherwise navigating website 106, as previously discussed. Atstep 426, the user 102 may checkout and purchase the domain namegenerated at step 422.

Turning now to FIG. 5, a flowchart illustrating a method by whichcandidate domain names can be generated for the user 102 based on inputdata 514 related to an advertising software application 508 or otheradvertising services is shown. The method shown in FIG. 5 may be useful,for example, to assist a user that already has a website, but wishes toadd advertising to the website. However, the user may be unaware thatthe domain name that they have selected for their existing website isnot particularly suited to the type of advertising that will bedisplayed thereon. In that case, the present method may be useful tomake recommendations of improved domain names for the user that the usermay wish to register at the same time the advertising services arepurchased.

The user 102 in this case may be an existing user and may begin byaccessing the website 106. The user 102 may be any Internet user, forexample, who may wish to incorporate advertising into an existingwebsite hosted at a particular domain name. As such, the user accessesthe website 106 to execute advertising software application 508, whichis configured to assist the user 102 in incorporating advertising intothe user's website.

In step 500, the user 102 is authenticated as a user having an existingwebsite. At step 506, the website 106 provides the user 102 theadvertising software application 508, which allows the user 102 to addadvertising features to their existing website.

At step 510, a website information form 1032, as shown in FIG. 10, canbe provided to the user 102 on a website information page 1034requesting that the user provide information useful for theincorporation of advertising content into the user's website. Thewebsite information form 1032 may enable the user 102 to provide inputdata 514 that includes, but is not limited to, a title (e.g., a businessname), a location (e.g., home and/or business address, city, state, zipcode, etc.), a phone number, features relevant to the user's 102products and services, email address, business website, businesstagline, business category, text, and metadata such as images providedby the user 102 or the website 106 at step 512. The server 110 shown inFIG. 1 acquires data from the user 102 as the business information form1032 is filled out. At this point, the system 100 also knows the domainname of the user's existing website and can thereby access the user'sexisting website to collect one or more keywords therefrom. Accordingly,at step 512, the system 100 may automatically scrape the user's 102existing website using web scraping software capable of scraping all thepages on the user's 102 existing website to gather data including, butnot limited to page titles, business location data, product features andservices, metadata from images and pages, etc. to generate the keywordcollection. Additionally, if an advertising campaign has been in placefor some time for the web site, the collection of keywords may includekeywords that are determined to have performed well in the advertisingcampaign.

As the user 102 is providing the input data 514, the system 100 may beconfigured to acquire additional data about the user 102 from thirdparty data sources 504 at step 516. For example, if the user 102provides their first and last name on the business information form, thesystem 100 may run a search on the third party data sources 504 usingthe user's 102 first and last name to gather additional informationabout the user 102. The third party data sources 504 may include, butare not limited to, LINKEDIN, FACEBOOK, YELP, TWITTER and a State Bardirectory. As a non-limiting example, the system 100 may run a search onFacebook.com using the first and last name provided by the user 102. Thesystem 100 may gather information from Facebook.com, such as where theuser 102 is from (i.e., city and state), where they are employed, whatcollege they attended, etc.

The system 100 provides an integration module (not shown) to generate akeyword collection at step 518. The keyword collection may contain, forexample, keywords related to the user 102 acquired at steps 512 and 516and generated by analysis of the user's existing website. These keywordswill be used to generate a candidate domain name for the user 102, aswill be discussed in further detail below.

At step 526, the system 100 generates a number of candidate domain namesfor the user using the keyword collection and the information collectedin steps 512 and 516. In one implementation, before performing step 526,the system 100 may first determine a quality rating for the user'sexisting website. For example, the system may determine a search enginevisibility rating, for example, of the user's 102 existing domain namebased on the input data 514. The search engine visibility rating, may bea numerical rating, for example, that indicates whether the user'sexisting domain name is highly visible or not when other users performqueries on search engines such as, BING, YAHOO, GOOGLE, AOL, etc. If thesearch engine visibility rating for the user's existing domain name issufficiently low (e.g., below a pre-determined threshold), the system100 may generate the candidate domain names for the user 102 based ontheir existing search engine visibility rating and the keywordcollection generated at step 518. The candidate domain names displayedwill therefore be relevant to the user 102 and, specifically, the user'swebsite. The use of any one of the domain names generated at step 526may increase the website's traffic, and consequently, sales if theuser's 102 website hosts an online store, for example.

Once the candidate domain names are generated based on the keywordcollection at step 526, the system 100 may provide the user 102 anoption to add one or more of the candidate domain names to theirshopping cart at step 528 for purchase. Step 528 may occur, for example,as the user is going through a checkout process 112 for the advertisingsoftware application 508, as previously discussed with respect to FIG.8C. At step 538, the user 102 may checkout and purchase the advertisingservices and, optionally, the domain name generated at step 526.

In some cases, the candidate domain names will be displayed on a userinterface utilized by a user to monitor their advertising campaign. Forexample, FIG. 11 depicts user interface 1100. User interface 1100provides a dashboard enabling a user to review the status of theircurrent advertising or marketing campaign and provides information suchas the number of impressions and clicks the web page has received, aswell as a budget status of the advertising campaign. As the campaignproceeds, and certain keywords in the campaign are identified asgenerating increased traffic, candidate domain names can be generatedbased upon those successful keywords. Once generated, those candidatedomain names can be provided to the user for potential purchase orregistration. As such, user interface 1100 includes candidate domainname 1134. The user 102 may choose to add the candidate domain name 1134to their shopping cart by selecting an ‘Add’ button 1136. The user willthen be given an opportunity to purchase or register the domain name.

Several different environments may be used to accomplish the steps ofembodiments disclosed herein. FIGS. 6 and 7 demonstrate a streamlinedexample of such an environment and illustrate a non-limiting example ofa system and/or structure that may be used to accomplish the methods andembodiments disclosed and described herein. Such methods may beperformed by any central processing unit (CPU) in any computing system,such as a microprocessor running on at least one server 610 and/orclient 620, and executing instructions stored (perhaps as scripts and/orsoftware, possibly as software modules) in computer-readable mediaaccessible to the CPU, such as a hard disk drive on a server 610 and/orclient 620.

The example embodiments herein place no limitations on whom or what maycomprise users. Thus, as non-limiting examples, users may comprise anyindividual, entity, business, corporation, partnership, organization,governmental entity, and/or educational institution.

The example embodiments shown and described herein exist within theframework of a network 600 and should not limit possible networkconfiguration or connectivity. Such a network 600 may comprise, asnon-limiting examples, any combination of the Internet, the publicswitched telephone network, the global Telex network, computer networks(e.g., an intranet, an extranet, a local-area network, or a wide-areanetwork), a wired network, a wireless network, a telephone network, acorporate network backbone or any other combination of known or laterdeveloped networks.

At least one server 610 and at least one client 620 may becommunicatively coupled to the network 600 via any method of networkconnection known in the art or developed in the future including, butnot limited to wired, wireless, modem, dial-up, satellite, cable modem,Digital Subscriber Line (DSL), Asymmetric Digital Subscribers Line(ASDL), Virtual Private Network (VPN), Integrated Services DigitalNetwork (ISDN), X.25, Ethernet, token ring, Fiber Distributed DataInterface (FDDI), IP over Asynchronous Transfer Mode (ATM), InfraredData Association (IrDA), wireless, WAN technologies (T1, Frame Relay),Point-to-Point Protocol over Ethernet (PPPoE), and/or any combinationthereof.

The server(s) 610 and client(s) 620 (along with software modules and thedata storage 630 disclosed herein) may be communicatively coupled to thenetwork 600 and to each other in such a way as to allow the exchange ofinformation required to accomplish the method steps disclosed herein,including, but not limited to receiving the information from a userinterface on one or more clients 620, and one or more servers 610receiving the information.

The client 620 may be any computer or program that provides services toother computers, programs, or users either in the same computer or overa computer network 600. As non-limiting examples, the client 620 may bean application, communication, mail, database, proxy, fax, file, media,web, peer-to-peer, or standalone computer, cell phone, “smart” phone,personal digital assistant (PDA), etc. which may contain an operatingsystem, a full file system, a plurality of other necessary utilities orapplications or any combination thereof on the client 620. Non limitingexample programming environments for client applications may includeJavaScript/AJAX (client side automation), ASP, JSP, Ruby on Rails,Python's Django, PHP, HTML pages or rich media like Flash, Flex,Silverlight, any programming environments for mobile “apps,” or anycombination thereof.

The client computer(s) 620 which may be operated by one or more usersand may be used to connect to the network 600 to accomplish theillustrated embodiments may include, but are not limited to, a desktopcomputer, a laptop computer, a hand held computer, a terminal, atelevision, a television set top box, a cellular phone, a wirelessphone, a wireless hand held device, a “smart” phone, an Internet accessdevice, a rich client, thin client, or any other client functional witha client/server computing architecture. Client software may be used forauthenticated remote access to one more hosting computers or servers,described below. These may be, but are not limited to being accessed bya remote desktop program and/or a web browser, as are known in the art.

The user interface displayed on the client(s) 620 or the server(s) 610may be any graphical, textual, scanned and/or auditory information acomputer program presents to the user, and the control sequences such askeystrokes, movements of the computer mouse, selections with a touchscreen, scanned information etc. used to control the program. Examplesof such interfaces include any known or later developed combination ofGraphical User Interfaces (GUI) or Web-based user interfaces as seen inand after FIG. 8A, including Touch interfaces, Conversational InterfaceAgents, Live User Interfaces (LUI), Command line interfaces, Non-commanduser interfaces, Object-oriented User Interfaces (OOUI) or Voice userinterfaces. Any information generated by the user, or any otherinformation, may be accepted using any field, widget and/or control usedin such interfaces, including but not limited to a text-box, text field,button, hyper-link, list, drop-down list, check-box, radio button, datagrid, icon, graphical image, embedded link, etc.

The software modules used in the context of the current invention may bestored in the memory of—and run on—at least one server 610 and/or client620. The software modules may comprise software and/or scriptscontaining instructions that, when executed by a microprocessor on aserver 610 and/or client 620, cause the microprocessor to accomplish thepurpose of the module or the methods disclosed herein.

The software modules may interact and/or exchange information via anApplication Programming Interface or API. An API may be asoftware-to-software interface that specifies the protocol defining howindependent computer programs interact or communicate with each other.The API may allow a requesting party's software to communicate andinteract with the software application and/or its provider-perhaps overa network-through a series of function calls (requests for services). Itmay comprise an interface provided by the software application and/orits provider to support function calls made of the software applicationby other computer programs, perhaps those utilized by the requestingparty to provide information for publishing or posting domain name andhosted website information.

The API may comprise any API type known in the art or developed in thefuture including, but not limited to, request-style, Berkeley Sockets,Transport Layer Interface (TLI), Representational State Transfer (REST),SOAP, Remote Procedure Calls (RPC), Standard Query Language (SQL), filetransfer, message delivery, and/or any combination thereof.

The software modules may also include mobile applications, possibly on aclient computer and/or mobile device. These mobile applications, or“apps” may comprise computer software designed to help people perform anactivity and designed to help the user to perform singular or multiplerelated specific tasks. It helps to solve problems in the real world bymanipulating text, numbers, graphics, or a combination of theseelements.

The server(s) utilized within the disclosed system 610 may comprise anycomputer or program that provides services to other computers, programs,or users either in the same computer or over a computer network 600. Asnon-limiting examples, the server 610 may comprise application,communication, mail, database, proxy, fax, file, media, web,peer-to-peer, standalone, software, or hardware servers (i.e., servercomputers) and may use any server format known in the art or developedin the future (possibly a shared hosting server, a virtual dedicatedhosting server, a dedicated hosting server, a cloud hosting solution, agrid hosting solution, or any combination thereof).

The server 610 may exist within a server cluster, as illustrated. Theseclusters may include a group of tightly coupled computers that worktogether so that in many respects they can be viewed as though they area single computer. The components may be connected to each other throughfast local area networks which may improve performance and/oravailability over that provided by a single computer.

The server(s) 610 or software modules within the server(s) 610 may usequery languages such as MSSQL or MySQL to retrieve the content from datastorage 630. Server-side scripting languages such as ASP, PHP, CGI/Perl,proprietary scripting software/modules/components etc. may be used toprocess the retrieved data. The retrieved data may be analyzed in orderto determine information recognized by the scripting language,information to be matched to those found in data storage, availabilityof requested information, comparisons to information displayed andinput/selected from the user interface or any other content retrievalwithin the method steps disclosed herein.

The server 610 and/or client 620 may be communicatively coupled to datastorage 630 to retrieve any information requested. The data storage 630may be any computer components, devices, and/or recording media that mayretain digital data used for computing for some interval of time. Thestorage may be capable of retaining stored content for any datarequested, on a single machine or in a cluster of computers over thenetwork 600, in separate memory areas of the same machine such asdifferent hard drives, or in separate partitions within the same harddrive, such as a database partition.

Non-limiting examples of the data storage 630 may include, but are notlimited to, a Network Area Storage, (“NAS”), which may be aself-contained file level computer data storage connected to andsupplying a computer network with file-based data storage services. Thestorage subsystem may also be a Storage Area Network (“SAN”—anarchitecture to attach remote computer storage devices to servers insuch a way that the devices appear as locally attached), an NAS-SANhybrid, any other means of central/shared storage now known or laterdeveloped or any combination thereof.

Structurally, the data storage 630 may comprise any collection of data.As non-limiting examples, the data storage 630 may comprise a localdatabase, online database, desktop database, server-side database,relational database, hierarchical database, network database, objectdatabase, object-relational database, associative database,concept-oriented database, entity-attribute-value database,multi-dimensional database, semi-structured database, star schemadatabase, XML database, file, collection of files, spreadsheet, and/orother means of data storage such as a magnetic media, hard drive, otherdisk drive, volatile memory (e.g., RAM), non-volatile memory (e.g., ROMor flash), and/or any combination thereof.

As seen in FIG. 6, the server(s) 610 and data storage 630 may existand/or be hosted in one or more data centers (640, 650). These datacenters 640/650 may provide hosting services for websites, services orsoftware relating to stored information, or any related hosted websiteincluding, but not limited to hosting one or more computers or serversin a data center 640/650 as well as providing the general infrastructurenecessary to offer hosting services to Internet users includinghardware, software, Internet web sites, hosting servers, and electroniccommunication means necessary to connect multiple computers and/orservers to the Internet or any other network 600. These data centers640/650 or the related clients 620 may accept messages from textmessages, SMS, web, mobile web, instant message, third party APIprojects or other third party applications.

As users access and/or input information, this information may beredirected and distributed between and among the data centers (640, 650)via commands from any combination of software modules hosted on theserver(s) 610 and executed via processors on the server(s) 610. Thisinformation may then be accessed and manipulated by the combination ofsoftware modules or stored in the data storage 630 of any of a pluralityof data centers, either separate from or integrated into the one or moreservers, so that the information is available to be searched andaccessed by the user and/or any other components of any or all datacenters.

Any references to “software combination,” “combination of software,”“combination of software modules” etc. referred to herein may includeany combination of software modules executed by a microprocessor oneither the server 610 or client 620 computers. These software modulesmay also be used in combination with any other hardware or softwarestructures disclosed herein. The servers 610 may be hosted in any datacenter (640, 650) operated by any hosting provider such as thosedisclosed herein and the servers 610 and clients 620 may be operated byany users disclosed herein.

The system also may comprise a domain name generation module 660 thatmay be stored in the memory of—and run on—at least one server 610 andmay comprise any software and/or scripts containing instructions that,when executed by the server's 610 microprocessor, cause themicroprocessor to generate a domain name relevant to the keywordcollection. As illustrated in FIG. 7, the domain name generation module660 may comprise an information source receipt module 680 and a keywordextraction and combination module 690. The information source receiptmodule 680 may comprise scripts and/or software running on the server610 that operates to obtain a plurality of data from any informationsource. As described in detail above, the information source forming thebasis of generated domain names may comprise any collection of data,accessible to the domain name generation module 660 that may containdata regarding the user and/or the user's business, for example,including, but not limited to websites, web pages, news feeds, and/orReal Simple Syndication (RSS) feeds.

The keyword extraction and combination module 690 also may comprisesoftware and/or scripts running on the server 610 and may operate toparse received data into a plurality of keywords, combine keywords intoa root name, and concatenate a top level domain to the root name,thereby generating the candidate or alternate domain name. In onepossible embodiment, the keyword extraction and combination module 690also may determine a topic to which each keyword relates, sort thekeywords into subcategories according to topic, and generate a root nameby combining keywords from the same subcategory. A domain name relevantto the keyword collection is thereby generated after a TLD isconcatenated to the root name. Modules 680 and 690 may comprise anysoftware and/or scripts running on the server 210 that may accomplishthe methods described in detail above.

The system also may comprise a domain name registration module 670running on at least one server 610 and offering the generated domainname for registration (if available). This module may comprise softwareand/or scripts containing instructions that, when executed by theserver's 610 microprocessor, cause the microprocessor to determinewhether the domain name is available for registration and provide thedomain name for registration, if available. Additionally, the domainname registration module 670 may, if the domain name is available,register the domain name to the registrant. It may comprise any domainname registration system known in the art or developed in the futureincluding, but not limited to, a website enabled domain name purchaseand registration system, such as that described in detail above and/ormay be available on GODADDY.COM's website. The domain names database maycomprise, as non-limiting examples, a local database, online database,desktop database, server-side database, relational database,hierarchical database, network database, object database,object-relational database, associative database, concept-orienteddatabase, entity-attribute-value database, multi-dimensional database,semi-structured database, star schema database, XML database, file,collection of files, spreadsheet, or other means of data storage locatedon a computer, client, server, or any other storage device known in theart or developed in the future.

The present disclosure describes preferred embodiments with reference tothe Figures, in which like numbers represent the same or similarelements. Reference throughout this specification to “one embodiment,”“an embodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “in one embodiment,” “in an embodiment,” andsimilar language throughout this specification may, but do notnecessarily, all refer to the same embodiment.

The described features, structures, or characteristics of the inventionmay be combined in any suitable manner in one or more embodiments. Inthe description, numerous specific details are recited to provide athorough understanding of embodiments of the invention. One skilled inthe relevant art will recognize, however, that the invention may bepracticed without one or more of the specific details, or with othermethods, components, materials, and so forth. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

The schematic flow chart diagrams included are generally set forth aslogical flow-chart diagrams. As such, the depicted order and labeledsteps are indicative of one embodiment of the presented method. Othersteps and methods may be conceived that are equivalent in function,logic, or effect to one or more steps, or portions thereof, of theillustrated method. Additionally, the format and symbols employed areprovided to explain the logical steps of the method and are understoodnot to limit the scope of the method. Although various arrow types andline types may be employed in the flow-chart diagrams, they areunderstood not to limit the scope of the corresponding method. Indeed,some arrows or other connectors may be used to indicate only the logicalflow of the method. For instance, an arrow may indicate a waiting ormonitoring period of unspecified duration between enumerated steps ofthe depicted method. Additionally, the order in which a particularmethod occurs may or may not strictly adhere to the order of thecorresponding steps shown.

The present invention has been described in terms of one or morepreferred embodiments, and it should be appreciated that manyequivalents, alternatives, variations, and modifications, aside fromthose expressly stated, are possible and within the scope of theinvention.

The invention claimed is:
 1. A method, comprising: receiving, by atleast one server communicatively coupled to a network, a request toaccess or purchase access to a software application, the request beingreceived from a user; generating, by the at least one server, keywordsassociated with at least one of the user, a website of the user, and abusiness of the user; generating, by the at least one server, acandidate domain name relevant to the keywords; and displaying, by theat least one server, a user interface including the candidate domainname, the user interface enabling the user to register the candidatedomain name.
 2. The method of claim 1, wherein identifying the keywordsincludes, in response to the request, prompting the user to complete anorder form for the software application.
 3. The method of claim 1,wherein the software application includes a website builder, a websitehosting application, an advertising application, a storage application,or an email application.
 4. The method of claim 1, wherein the keywordsassociated with at least one of the user and the website of the userincludes at least one of a business name and a business description. 5.The method of claim 1, wherein identifying the keywords includesacquiring data from a third party data source.
 6. The method of claim 1,wherein the user interface includes an option to purchase access to thesoftware application.
 7. The method of claim 1, wherein the userinterface provides the software application.
 8. The method of claim 7,wherein the software application is a website builder application. 9.The method of claim 8, wherein identifying the keywords includesanalyzing data entered into the website builder application by the user.10. A method, comprising: receiving, by at least one servercommunicatively coupled to a network, data relating to interactions of auser with a website; generating keywords associated with at least one ofthe user, a website of the user, and a business of the user based on theinteractions of the user; generating, by the at least one server, acandidate domain name relevant to the keywords; and returning, by the atleast one server, the candidate domain name.
 11. The method of claim 10,wherein the interactions include requesting, from the website,information describing a software application.
 12. The method of claim11, wherein the software application includes a website builder, awebsite hosting application, an advertising application, a storageapplication, or an email application.
 13. The method of claim 10,wherein the keywords associated with at least one of the user and thewebsite of the user include at least one of a business name and abusiness description.
 14. The method of claim 10, wherein identifyingthe keywords includes acquiring data from a third party data source. 15.The method of claim 10, wherein the interactions include entering datainto a website builder application.
 16. A system, comprising: at leastone server computer in communication with a network, the at least oneserver computer including a processor configured to: receive a requestto access or purchase access to a software application, the requestbeing received from a user; generate keywords associated with at leastone of the user, a website of the user, and a business of the user;generate a candidate domain name relevant to the keywords; and display auser interface including the candidate domain name, the user interfaceenabling the user to register the candidate domain name.
 17. The systemof claim 16, wherein identifying the keywords includes, in response tothe request, prompting the user to complete an order form for thesoftware application.
 18. The system of claim 16, wherein the softwareapplication includes a website builder, a website hosting application,an advertising application, a storage application, or an emailapplication.
 19. The system of claim 16, wherein identifying thekeywords includes acquiring data from a third party data source.
 20. Thesystem of claim 16, wherein identifying the keywords includes analyzingdata entered into the website builder application by the user.